home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Wildcat Gold - The Optical BBS
/
Wildcat Gold - The Optical BBS (The Golden ROM Series)(Volume 4 Number 1)(The Digital Publishing Company)(1992).ISO
/
sdn
/
drpcp1.sdn
/
TBLSHT01
< prev
next >
Wrap
Text File
|
1991-11-25
|
8KB
|
263 lines
Problem: My log on script won't work now. It did before!
Solution: The service it was written for has changed their log on proce-
dure. or ProComm can't find the script file. If the problem is
a change in log on procedure, you'll have to edit the script or
record it again. If the problem is because ProComm can't find
the script file:
KEYSTROKES: ┌─────┐ ┌─────┐
│ ALT │ + │ F 7 │
└─────┘ └─────┘
┌─────┐
│ Enter the correct PATH.
└─────┘
┌────────┐
│ ENTER │
└────────┘
Problem: My modem hangs up unexpectedly. This happens intermittently and
only occasionally.
Solution: The problem is usually call waiting. Call the telephone company
about how to go about disabling it.
Problem: Binary file transfer aborts.
Solution: This usually hppens because the transfer protocols don't match,
thre's too many errors during the transfer, or somebody in the
place picked up another phone on the same line. You can restart
the transfer using the correct protocol, hang up and redial, or
secure all the telephones and restart the transfer.
Problem: ASCII uploads stall on me.
Solution: Usually this happens because you are trying to send an ASCII
file using a binary transfer protocol like XMODEM <GLOSSARY 9 15>
or you have set the ASCII transfer options incorrectly.
<GLOSSARY 1 11>
KEYSTROKES: ┌─────┐
│ ESC │
Correcting the └─────┘
problem using ┌─────┐
non-ASCII │ Restart transfer with ASCII protocol setting.
transfer └─────┘
protocol.
KEYSTROKES: ┌─────┐ ┌─────┐
│ ALT │ + │ S │
Wrong ASCII └─────┘ └─────┘
tranfer set- ┌─────┐
tings. │ A │
└─────┘
┌─────┐
│ Change the settings.
└─────┘
┌─────┐┌─────┐┌─────┐
│ ESC ││ S ││ ESC │
└─────┘└─────┘└─────┘
Problem: Incoming text is garbled.
Solution: The wrong terminal parameters are set.
KEYSTROKES: ┌─────┐ ┌─────┐ <PROGPRAM>
│ ALT │ + │ P │
└─────┘ └─────┘
┌─────┐
│ Select new parameters.
└─────┘
┌─────┐ ┌─────┐
│ ALT │ + │ S │
└─────┘ └─────┘
Problem: When I'm in a session, I get double-spaced text!
Solution: You're getting extra linefeeds. You need to turn them off, you
can do that by:
KEYSTROKES: ┌─────┐ ┌─────┐
│ ALT │ + │ F 3 │
└─────┘ └─────┘
Problem: All text appears on one line and nothing seems to wrap around.
Solution: You don't have Linefeeds enabled.
KEYSTROKES: ┌─────┐ ┌─────┐
│ ALT │ + │ F 3 │
└─────┘ └─────┘
Problem: Some incoming characters are dropped when I'm in a session.
Solution: The problem is usually a conflict with a Terminate and Stay
Resident (TSR) program. Disable the TSR and try again.
Problem: I can't seem to get the modem to dial.
Solution: If it's an external modem, the power could be off. Also, the
phone could be unplugged or another phone in use. ProComm could
be looking on the wrong COM port for the modem, if that's the
problem:
KEYSTROKES: ┌─────┐ ┌─────┐ <PROGPRAM>
│ ALT │ + │ P │
└─────┘ └─────┘
┌─────┐
│ Select new COM port.
└─────┘
┌─────┐ ┌─────┐
│ ALT │ + │ S │
└─────┘ └─────┘
Problem: Every time I try to dial someone, ProComm hangs up the phone
before I get a connection.
Solution: Either the phone line is busy or the `Wait for redial' program
time eter is too short. If the line is busy, redialing it will
solve the problem. If the `Wait for redial' time is too short:
KEYSTROKES: ┌─────┐ ┌─────┐ <PDIAL>
│ ALT │ + │ S │
└─────┘ └─────┘
┌─────┐┌─────┐┌─────┐
│ M ││ G ││ F │
└─────┘└─────┘└─────┘
┌─────┐
│ Enter a longer wait time.
└─────┘
┌────────┐
│ ENTER │
└────────┘
┌─────┐┌─────┐┌─────┐┌─────┐
│ ESC ││ ESC ││ S ││ ESC │
└─────┘└─────┘└─────┘└─────┘
Problem: When using the redial facility, or making a call from a command
file, the program doesn't realize when I've made a connection.
Solution: Make sure that ProComm's modem connect string is correctly
defined for the message your modem returns for when a connection
is made. The ProComm default is "CONNECT". <MODEM>
Problem: I sometimes have trouble opening files for logging or down-
loading. That is, sometimes the download or log features don't
seem to work.
Solution: You may need to increase the FILES= parameter in your CONFIG.SYS
file. We suggest using at least FILES=20. Consult your DOS
manual for more details.
Problem: I can't get the dialing directory to call using the long dis-
tance code I've put in the number.
Solution: Specify the long distance code to be used when you make the call
itself, not when you enter the number into the directory. For
instance, say "#37" at the "==>" prompt to dial entry number 37
using the '#' long distance code. Entering a long distance code
as part of the number will not work. <PDIAL 14 2>
Problem: I don't seem to have a dialing directory.
Solution: ProComm can't find the directory file.
KEYSTROKES: ┌─────┐ ┌─────┐ <PROGPRAM>
│ ALT │ + │ F 7 │ <PDIAL>
└─────┘ └─────┘
┌─────┐
│ Enter new path/filename.
└─────┘
┌────────┐
│ ENTER │
└────────┘
Problem: I'm having trouble getting ProComm to work with my PCjr. Any
ideas?
Solution: The PCjr is somewhat different in the way it handles communica-
tions. A solution that has worked for a number of users is
this: Call our BBS and download a file called COMSWAP.ARC.
After un-arcing the file you should find 2 programs called
COMSWAP.COM and COMREST.COM. Run COMSWAP before running ProComm
and run COMREST after. Then use ProComm set to COM2:.
Problem: When I'm using a multi-tasking operating system and running
ProComm in the background, window displays bleed through to the
active partition.
Solution: Go into the general SetUp screen and set ProComm to use the BIOS
screen write method. It is much slower but will not cause the
bleed through that you are experiencing.
